Techniques and architectures for selective obfuscation of personally identifiable information (PII) in environments capable of replicating data

ABSTRACT

Within one or more instances of a computing environment where an instance is a self-contained architecture to provide at least one database with corresponding search and file system. User information from the one or more instances of the computing environment is organized as zones. A zone is based on one or more characteristics of corresponding user information that are different than the instance to which the user information belongs. User information is selectively obfuscated prior to transmitting blocks of data including the obfuscated user information. The selective obfuscation is based on zone information for one or more zones to which the user information belongs.

CLAIM FOR PRIORITY

This application is a continuation of, and claims the benefit of, U.S.patent application Ser. No. 15/600,521 entitled “TECHNIQUES ANDARCHITECTURES FOR SELECTIVE OBFUSCATION OF PERSONALLY IDENTIFIABLEINFORMATION (PII) IN ENVIRONMENTS CAPABLE OF REPLICATING DATA”, filedMay 19, 2017, which claims the benefit of U.S. Provisional PatentApplication No. 62/501,003 entitled “TECHNIQUES AND ARCHITECTURES FORSELECTIVE OBFUSCATION OF PERSONALLY IDENTIFIABLE INFORMATION (PII) INENVIRONMENTS CAPABLE OF REPLICATING DATA”, filed May 3, 2017, the entirecontents of which are incorporated herein by reference.

TECHNICAL FIELD

Embodiments relate to techniques for managing replication of data. Moreparticularly, embodiments relate to techniques for selectivelyobfuscating selected data (e.g., personally identifiable information)when replicating data.

BACKGROUND

Data replication generally refers to the process of copying data. Datareplication is a common technique to provide data synchronization aswell as other advantages. Data replication is usually an ongoing processin which transactions or other data sets are copied and stored inmultiple locations. However, there are conditions under which certaindata should not be replicated in the standard manner. This has been acomplex situation that has been difficult to solve in a clean andefficient manner.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments of the invention are illustrated by way of example, and notby way of limitation, in the figures of the accompanying drawings inwhich like reference numerals refer to similar elements.

FIG. 1 is one embodiment of a simple replication architecture.

FIG. 2 is a flow diagram of one embodiment of a technique forselectively obfuscating personally identifiable information (PII).

FIG. 3 illustrates a block diagram of an environment where an on-demanddatabase service might be used.

FIG. 4 illustrates a block diagram of an environment where an on-demanddatabase service might be used.

DETAILED DESCRIPTION

In the following description, numerous specific details are set forth.However, embodiments of the invention may be practiced without thesespecific details. In other instances, well-known structures andtechniques have not been shown in detail in order not to obscure theunderstanding of this description.

As used herein, tenant includes a group of users who share a commonaccess with specific privileges to a software instance. A multi-tenantarchitecture provides a tenant with a dedicated share of the softwareinstance typically including one or more of tenant specific data, usermanagement, tenant-specific functionality, configuration,customizations, non-functional properties, associated applications, etc.Multi-tenancy contrasts with multi-instance architectures, whereseparate software instances operate on behalf of different tenants.

FIG. 1 is one embodiment of a simple replication architecture.Replication is a process where each database instance (e.g., 100, 150)exchanges modified database records for a set of tables with all otherinstances. The example of FIG. 1 includes only two instances, but anynumber of instances can be supported. The goal is for replicated tablesto be identical everywhere. To support this, processes running withinthe instances should see an integrated view of the replicated data.

In one embodiment, a group of tenants (or organizations) are groupedtogether in an instance, or a pod. In instance is a self-contained unitthat has all that is required to provide a multitenant platformincluding, for example, one or more application servers, one or moredatabase servers, at least one database, search and file systems, etc.Each tenant/organization is allocated a pod in which their data resides.

For example, a replicated table can have user information from all usersfrom all instances (e.g., core.all_users) so that users can have accessregardless of the instance they are connected to. In many cases, thereplication process runs continually in the background on everyinstance. Each instances accts as a client (e.g., 120, 170) to ask allknown peers for updates and as a server (e.g., 130, 180) to provide datato all known peers. However, as discussed herein, replication of somedata can have data residency restrictions.

In one embodiment, each instance detects changes to data made withinthat instance and can package change information into chunks havingassociated metadata about the changes. These chunks are sent to otherinstances where they are persisted locally and applied (e.g., upserted)to the corresponding table. In addition to serving their own changes,instances can also act as a proxy for changes made elsewhere (e.g., ifthey are acting as a “leader” of a pod or data center), in which casepeers can request changes that are not their own and the server canreply with a local copy of the changes.

As described herein, replication mechanisms can be provided thatdetermine whether to obfuscate one or more fields in a replicated entitybased on properties of a source zone or pod. In one embodiment, all podsare designated either “standard” or “public,” but additional and/ordifferent designations could also be supported. In various embodiments,unobfuscated replication is not allowed for personally identifiableinformation (PII) flowing from standard to public pods.

In various embodiments, one or more pods can be grouped into a zone.Zones can be based on, for example, geography. Zones can be based onother considerations as well, for example, security considerations,licensing levels, customer type. In one embodiment, a zone can be asubset of a data center. In another embodiment, a zone can includesubsets of multiple data centers so that the zone spans multiple datacenters. Conceptually, a zone is a layer above a data center. Thetechniques described herein can be useful to, for example, prevent PIIdata from leaving a set of pods that have data residency requirements.

Many of the examples provided herein are related to data residencyand/or data sovereignty requirements; however, the embodiments describedherein are more broadly applicable. Data residency and data sovereigntyrefer to the physical location and legal requirements for data stored inthe corresponding geographic location.

Each jurisdiction (e.g., United States, European Union) can have its owndata residency laws and requirements. These laws and requirements cancontrol what data is used (including movement of data) and what datashould be protected. For example, the European Union has privacy lawsrelating to PII. Entities that store and utilize data must comply withthese laws and requirements.

Various embodiments are described that can be utilized to comply withdata residency requirements. In one example embodiment, four servercategories are utilized: 1) Standard; 2) Standard Data Residency; 3)Public; and 4) Public Data Residency. Using these four categories thefollowing three data residency requirements can be enforced: 1) PIIcannot leave Standard Data Residency servers unobfuscated; 2) PII datais not sent to Public or Public Data Residency servers unobfuscated; and3) PII data in a Public server does not leave its geographic region.This is but one example of a configuration to manage data with specificdata residency requirements. Other configurations can also be supported.

In one embodiment, replication includes four basic processes: 1) changedetection; 2) change serving; 3) change requests; and 4) change upserts.Techniques for each of these processes are described in greater detailbelow; however, different techniques can also be utilized.

When a row in a replicated table (e.g., core.all_users) is modified, adatabase trigger writes to an indexing queue table (e.g.,core.last_unindexed), containing the partition, entity and date of thechange but not the specific rows that changed. A replication changedetection chron job periodically runs and pulls aggregates of changedrows and breaks them to manageable segments. The replicator createschunk definitions based on metadata and caches the chunks to thedatabase so that a subsequent database query is not needed. These chunkdefinitions are persisted in the database and are ready to serve. Thiscan result in virtual streams of chunks that are independent of eachother and can be processed in parallel.

In one embodiment, for deletes, in addition to triggering an indexer, atrigger that writes the deleted key to a table (e.g.,core.replication_record_deletion) can be utilized. These delete markersare treated as inserts and updates to that any query that getsmodifications from the underlying table gets both together.

In one embodiment, during the change detection process, the underlyingrecords are selected from the data base in order to determine thechunk's properties. In one embodiment, the process can cache aserialized version of the chunk immediately. In one embodiment, tosupport change detection, a replicated table has a modstamp (or similar)column and a server ID (or similar) column. In general, as a result ofthe change detection mechanism(s), any modification to the replicatedtable results in one or more chunks being created that the server canserve on request.

In one embodiment, serving data is a passive process. Requests can bemade over a HyperText Transfer Protocol (HTTP) and can be served by aservlet running on a web server. In one embodiment, the data areserialized on the server and deserialized by objects on the receivingclient.

In various embodiments, the techniques described herein can providedynamic management of PII protection based on zones and/or categories.In one embodiment, this provides the ability to virtually partition acloud-based environment to support multiple data residency requirementsbased on zones. That is, different data residencyrequirements/restrictions can be supported for different zones. In oneembodiment, each zone includes at least one pod, but pods are notrequired to be completely in the same physical location.

In one embodiment, obfuscation is accomplished utilizing a one-way hashfunction that is unique, but non-reversible. The original data isprotected because the process is non-reversible. The receivingentity/device receives an encrypted string generated from the originaldata, but because that encryption is non-reversible, the original data(e.g., PII) is protected. Using these techniques, the following PIIprotection requirements can be provided: PII data is not replicated inthe clear from a zone (or pod) of a first category (e.g., a public cloudpod), and PII data is not replicated in the clear from a secure zone (orpod) of a second category (e.g., a government pod, secure corporatezone). Additional and/or different categories can also be supported.

FIG. 2 is a flow diagram of one embodiment of a technique forselectively obfuscating personally identifiable information (PII). Whilethe techniques described with respect to FIG. 2 are directed to PII,these techniques can be used to protect other types of information, forexample, organizational information, financial information, etc.

The example of FIG. 2 assumes that data stored within the system hasbeen organized by zones, where zones are a layer above data centers,which can include one or more pods. In the example of FIG. 2, the zonesare based on geographic location (e.g., European Union, United States,United Kingdom, Portugal). Zones can be used to organize data innon-geographic groupings as well.

Continuing with the geographic region based zone architecture, each podcan be designated to a zone corresponding to the region in which the podresides. For example, a pod in a data center located in Italy can be inthe zone for Italy or for the European Union (EU). Thus, when data isreplicated (or otherwise copied or moved), the data residencyrequirements can be applied to the data moving out of the pod, ifnecessary.

Data stored in a computing environment can be organized in amulti-tiered structure with privacy, data residency and/or data securityrequirements associated with the data or the tiers, 210. In oneembodiment, the data is stored in an on-demand services environment thatcan also provide a multitenant architecture. Various embodiments foron-demand service environments are described in greater detail below.

In one embodiment, data is stored by computing platforms (e.g., servercomputer systems, desktop computer system) that are physically locatedin one or more data systems that are organized as pods, zones and/orother groupings. As discussed above, zones can be utilized to group podsby geography and apply data residency and/or PII protection requirementsand restrictions.

In one embodiment, zones can be groupings of pods based on geographicallocations of data and/or the source of data, each of which can have acorresponding restriction (or limitation) on how the data can behandled. In one embodiment, for example, a zone can correspond tonational boundaries such that all data centers within the nation are inthe same zone. Other zone configurations can be supported, for example,zones can correspond to service level agreements (SLAs), etc. In someembodiments, data obfuscation can be used to satisfy these requirements;however, in other embodiments, data movement or copying may beprevented.

A request to copy/move/replicate data is received, 220. As discussedabove, replication can be an ongoing process that periodically makesbackup copies of data and/or changes to existing data. The techniquesdescribed herein can also be applied to requests to copy and/or movedata. For example, if a user using a computing platform geographicallyoutside of the data residency zone, obfuscation can be applied to theresults of the request.

In response to the request, the receiving environment analyzes thestructure and corresponding requirements, 230, to determine what (ifany) data protection requirements should be applied in servicing therequest. In one embodiment, as discussed above, PII portions of therequested data can be obfuscated using various obfuscation techniques,240 after which the request can be serviced, 250. If obfuscation is notrequired, 230, the request can be serviced without obfuscation, 250.

FIG. 3 illustrates a block diagram of an environment 310 wherein anon-demand database service might be used. Environment 310 may includeuser systems 312, network 314, system 316, processor system 317,application platform 318, network interface 320, tenant data storage322, system data storage 324, program code 326, and process space 328.In other embodiments, environment 310 may not have all of the componentslisted and/or may have other elements instead of, or in addition to,those listed above.

Environment 310 is an environment in which an on-demand database serviceexists. User system 312 may be any machine or system that is used by auser to access a database user system. For example, any of user systems312 can be a handheld computing device, a mobile phone, a laptopcomputer, a work station, and/or a network of computing devices. Asillustrated in herein FIG. 3 (and in more detail in FIG. 4) user systems312 might interact via a network 314 with an on-demand database service,which is system 316.

An on-demand database service, such as system 316, is a database systemthat is made available to outside users that do not need to necessarilybe concerned with building and/or maintaining the database system, butinstead may be available for their use when the users need the databasesystem (e.g., on the demand of the users). Some on-demand databaseservices may store information from one or more tenants stored intotables of a common database image to form a multi-tenant database system(MTS). Accordingly, “on-demand database service 316” and “system 316”will be used interchangeably herein. A database image may include one ormore database objects. A relational database management system (RDMS) orthe equivalent may execute storage and retrieval of information againstthe database object(s). Application platform 318 may be a framework thatallows the applications of system 316 to run, such as the hardwareand/or software, e.g., the operating system. In an embodiment, on-demanddatabase service 316 may include an application platform 318 thatenables creation, managing and executing one or more applicationsdeveloped by the provider of the on-demand database service, usersaccessing the on-demand database service via user systems 312, or thirdparty application developers accessing the on-demand database servicevia user systems 312.

The users of user systems 312 may differ in their respective capacities,and the capacity of a particular user system 312 might be entirelydetermined by permissions (permission levels) for the current user. Forexample, where a salesperson is using a particular user system 312 tointeract with system 316, that user system has the capacities allottedto that salesperson. However, while an administrator is using that usersystem to interact with system 316, that user system has the capacitiesallotted to that administrator. In systems with a hierarchical rolemodel, users at one permission level may have access to applications,data, and database information accessible by a lower permission leveluser, but may not have access to certain applications, databaseinformation, and data accessible by a user at a higher permission level.Thus, different users will have different capabilities with regard toaccessing and modifying application and database information, dependingon a user's security or permission level.

Network 314 is any network or combination of networks of devices thatcommunicate with one another. For example, network 314 can be any one orany combination of a LAN (local area network), WAN (wide area network),telephone network, wireless network, point-to-point network, starnetwork, token ring network, hub network, or other appropriateconfiguration. As the most common type of computer network in currentuse is a TCP/IP (Transfer Control Protocol and Internet Protocol)network, such as the global internetwork of networks often referred toas the “Internet” with a capital “I,” that network will be used in manyof the examples herein. However, it should be understood that thenetworks that one or more implementations might use are not so limited,although TCP/IP is a frequently implemented protocol.

User systems 312 might communicate with system 316 using TCP/IP and, ata higher network level, use other common Internet protocols tocommunicate, such as HTTP, FTP, AFS, WAP, etc. In an example where HTTPis used, user system 312 might include an HTTP client commonly referredto as a “browser” for sending and receiving HTTP messages to and from anHTTP server at system 316. Such an HTTP server might be implemented asthe sole network interface between system 316 and network 314, but othertechniques might be used as well or instead. In some implementations,the interface between system 316 and network 314 includes load sharingfunctionality, such as round-robin HTTP request distributors to balanceloads and distribute incoming HTTP requests evenly over a plurality ofservers. At least as for the users that are accessing that server, eachof the plurality of servers has access to the MTS' data; however, otheralternative configurations may be used instead.

In one embodiment, system 316, shown in FIG. 3, implements a web-basedcustomer relationship management (CRM) system. For example, in oneembodiment, system 316 includes application servers configured toimplement and execute CRM software applications as well as providerelated data, code, forms, webpages and other information to and fromuser systems 312 and to store to, and retrieve from, a database systemrelated data, objects, and Webpage content. With a multi-tenant system,data for multiple tenants may be stored in the same physical databaseobject, however, tenant data typically is arranged so that data of onetenant is kept logically separate from that of other tenants so that onetenant does not have access to another tenant's data, unless such datais expressly shared. In certain embodiments, system 316 implementsapplications other than, or in addition to, a CRM application. Forexample, system 316 may provide tenant access to multiple hosted(standard and custom) applications, including a CRM application. User(or third party developer) applications, which may or may not includeCRM, may be supported by the application platform 318, which managescreation, storage of the applications into one or more database objectsand executing of the applications in a virtual machine in the processspace of the system 316.

One arrangement for elements of system 316 is shown in FIG. 3, includinga network interface 320, application platform 318, tenant data storage322 for tenant data 323, system data storage 324 for system data 325accessible to system 316 and possibly multiple tenants, program code 326for implementing various functions of system 316, and a process space328 for executing MTS system processes and tenant-specific processes,such as running applications as part of an application hosting service.Additional processes that may execute on system 316 include databaseindexing processes.

Several elements in the system shown in FIG. 3 include conventional,well-known elements that are explained only briefly here. For example,each user system 312 could include a desktop personal computer,workstation, laptop, PDA, cell phone, or any wireless access protocol(WAP) enabled device or any other computing device capable ofinterfacing directly or indirectly to the Internet or other networkconnection. User system 312 typically runs an HTTP client, e.g., abrowsing program, such as Edge from Microsoft, Safari from Apple, Chromefrom Google, or a WAP-enabled browser in the case of a cell phone, PDAor other wireless device, or the like, allowing a user (e.g., subscriberof the multi-tenant database system) of user system 312 to access,process and view information, pages and applications available to itfrom system 316 over network 314. Each user system 312 also typicallyincludes one or more user interface devices, such as a keyboard, amouse, touch pad, touch screen, pen or the like, for interacting with agraphical user interface (GUI) provided by the browser on a display(e.g., a monitor screen, LCD display, etc.) in conjunction with pages,forms, applications and other information provided by system 316 orother systems or servers. For example, the user interface device can beused to access data and applications hosted by system 316, and toperform searches on stored data, and otherwise allow a user to interactwith various GUI pages that may be presented to a user. As discussedabove, embodiments are suitable for use with the Internet, which refersto a specific global internetwork of networks. However, it should beunderstood that other networks can be used instead of the Internet, suchas an intranet, an extranet, a virtual private network (VPN), anon-TCP/IP based network, any LAN or WAN or the like.

According to one embodiment, each user system 312 and all of itscomponents are operator configurable using applications, such as abrowser, including computer code run using a central processing unitsuch as an Intel Core series processor or the like. Similarly, system316 (and additional instances of an MTS, where more than one is present)and all of their components might be operator configurable usingapplication(s) including computer code to run using a central processingunit such as processor system 317, which may include an Intel Coreseries processor or the like, and/or multiple processor units. Acomputer program product embodiment includes a machine-readable storagemedium (media) having instructions stored thereon/in which can be usedto program a computer to perform any of the processes of the embodimentsdescribed herein. Computer code for operating and configuring system 316to intercommunicate and to process webpages, applications and other dataand media content as described herein are preferably downloaded andstored on a hard disk, but the entire program code, or portions thereof,may also be stored in any other volatile or non-volatile memory mediumor device as is well known, such as a ROM or RAM, or provided on anymedia capable of storing program code, such as any type of rotatingmedia including floppy disks, optical discs, digital versatile disk(DVD), compact disk (CD), microdrive, and magneto-optical disks, andmagnetic or optical cards, nanosystems (including molecular memory ICs),or any type of media or device suitable for storing instructions and/ordata. Additionally, the entire program code, or portions thereof, may betransmitted and downloaded from a software source over a transmissionmedium, e.g., over the Internet, or from another server, as is wellknown, or transmitted over any other conventional network connection asis well known (e.g., extranet, VPN, LAN, etc.) using any communicationmedium and protocols (e.g., TCP/IP, HTTP, HTTPS, Ethernet, etc.) as arewell known. It will also be appreciated that computer code forimplementing embodiments can be implemented in any programming languagethat can be executed on a client system and/or server or server systemsuch as, for example, C, C++, HTML, any other markup language, Java™,JavaScript, ActiveX, any other scripting language, such as VBScript, andmany other programming languages as are well known may be used. (Java™is a trademark of Sun Microsystems, Inc.).

According to one embodiment, each system 316 is configured to providewebpages, forms, applications, data and media content to user (client)systems 312 to support the access by user systems 312 as tenants ofsystem 316. As such, system 316 provides security mechanisms to keepeach tenant's data separate unless the data is shared. If more than oneMTS is used, they may be located in close proximity to one another(e.g., in a server farm located in a single building or campus), or theymay be distributed at locations remote from one another (e.g., one ormore servers located in city A and one or more servers located in cityB). As used herein, each MTS could include one or more logically and/orphysically connected servers distributed locally or across one or moregeographic locations. Additionally, the term “server” is meant toinclude a computer system, including processing hardware and processspace(s), and an associated storage system and database application(e.g., OODBMS or RDBMS) as is well known in the art. It should also beunderstood that “server system” and “server” are often usedinterchangeably herein. Similarly, the database object described hereincan be implemented as single databases, a distributed database, acollection of distributed databases, a database with redundant online oroffline backups or other redundancies, etc., and might include adistributed database or storage network and associated processingintelligence.

FIG. 4 also illustrates environment 310. However, in FIG. 4 elements ofsystem 316 and various interconnections in an embodiment are furtherillustrated. FIG. 4 shows that user system 312 may include processorsystem 312A, memory system 312B, input system 312C, and output system312D. FIG. 4 shows network 314 and system 316. FIG. 4 also shows thatsystem 316 may include tenant data storage 322, tenant data 323, systemdata storage 324, system data 325, User Interface (UI) 430, ApplicationProgram Interface (API) 432, PL/SOQL 434, save routines 436, applicationsetup mechanism 438, applications servers 400 ₁-400 _(N), system processspace 402, tenant process spaces 404, tenant management process space410, tenant storage area 412, user storage 414, and application metadata416. In other embodiments, environment 310 may not have the sameelements as those listed above and/or may have other elements insteadof, or in addition to, those listed above.

User system 312, network 314, system 316, tenant data storage 322, andsystem data storage 324 were discussed above in FIG. 3. Regarding usersystem 312, processor system 312A may be any combination of one or moreprocessors. Memory system 312B may be any combination of one or morememory devices, short term, and/or long term memory. Input system 312Cmay be any combination of input devices, such as one or more keyboards,mice, trackballs, scanners, cameras, and/or interfaces to networks.Output system 312D may be any combination of output devices, such as oneor more monitors, printers, and/or interfaces to networks. As shown byFIG. 4, system 316 may include a network interface 320 (of FIG. 3)implemented as a set of HTTP application servers 400, an applicationplatform 318, tenant data storage 322, and system data storage 324. Alsoshown is system process space 402, including individual tenant processspaces 404 and a tenant management process space 410. Each applicationserver 400 may be configured to tenant data storage 322 and the tenantdata 323 therein, and system data storage 324 and the system data 325therein to serve requests of user systems 312. The tenant data 323 mightbe divided into individual tenant storage areas 412, which can be eithera physical arrangement and/or a logical arrangement of data. Within eachtenant storage area 412, user storage 414 and application metadata 416might be similarly allocated for each user. For example, a copy of auser's most recently used (MRU) items might be stored to user storage414. Similarly, a copy of MRU items for an entire organization that is atenant might be stored to tenant storage area 412. A UI 430 provides auser interface and an API 432 provides an application programmerinterface to system 316 resident processes to users and/or developers atuser systems 312. The tenant data and the system data may be stored invarious databases, such as one or more Oracle™ databases.

Application platform 318 includes an application setup mechanism 438that supports application developers' creation and management ofapplications, which may be saved as metadata into tenant data storage322 by save routines 436 for execution by subscribers as one or moretenant process spaces 404 managed by tenant management process 410 forexample. Invocations to such applications may be coded using PL/SOQL 434that provides a programming language style interface extension to API432. A detailed description of some PL/SOQL language embodiments isdiscussed in commonly owned U.S. Pat. No. 7,730,478 entitled, “Methodand System for Allowing Access to Developed Applicants via aMulti-Tenant Database On-Demand Database Service”, issued Jun. 1, 2010to Craig Weissman, which is incorporated in its entirety herein for allpurposes. Invocations to applications may be detected by one or moresystem processes, which manage retrieving application metadata 416 forthe subscriber making the invocation and executing the metadata as anapplication in a virtual machine.

Each application server 400 may be communicably coupled to databasesystems, e.g., having access to system data 325 and tenant data 323, viaa different network connection. For example, one application server 400₁ might be coupled via the network 314 (e.g., the Internet), anotherapplication server 400 _(N-1) might be coupled via a direct networklink, and another application server 400 _(N) might be coupled by yet adifferent network connection. Transfer Control Protocol and InternetProtocol (TCP/IP) are typical protocols for communicating betweenapplication servers 400 and the database system. However, it will beapparent to one skilled in the art that other transport protocols may beused to optimize the system depending on the network interconnect used.

In certain embodiments, each application server 400 is configured tohandle requests for any user associated with any organization that is atenant. Because it is desirable to be able to add and remove applicationservers from the server pool at any time for any reason, there ispreferably no server affinity for a user and/or organization to aspecific application server 400. In one embodiment, therefore, aninterface system implementing a load balancing function (e.g., an F5BIG-IP load balancer) is communicably coupled between the applicationservers 400 and the user systems 312 to distribute requests to theapplication servers 400. In one embodiment, the load balancer uses aleast connections algorithm to route user requests to the applicationservers 400. Other examples of load balancing algorithms, such as roundrobin and observed response time, also can be used. For example, incertain embodiments, three consecutive requests from the same user couldhit three different application servers 400, and three requests fromdifferent users could hit the same application server 400. In thismanner, system 316 is multi-tenant, wherein system 316 handles storageof, and access to, different objects, data and applications acrossdisparate users and organizations.

As an example of storage, one tenant might be a company that employs asales force where each salesperson uses system 316 to manage their salesprocess. Thus, a user might maintain contact data, leads data, customerfollow-up data, performance data, goals and progress data, etc., allapplicable to that user's personal sales process (e.g., in tenant datastorage 322). In an example of a MTS arrangement, since all of the dataand the applications to access, view, modify, report, transmit,calculate, etc., can be maintained and accessed by a user system havingnothing more than network access, the user can manage his or her salesefforts and cycles from any of many different user systems. For example,if a salesperson is visiting a customer and the customer has Internetaccess in their lobby, the salesperson can obtain critical updates as tothat customer while waiting for the customer to arrive in the lobby.

While each user's data might be separate from other users' dataregardless of the employers of each user, some data might beorganization-wide data shared or accessible by a plurality of users orall of the users for a given organization that is a tenant. Thus, theremight be some data structures managed by system 316 that are allocatedat the tenant level while other data structures might be managed at theuser level. Because an MTS might support multiple tenants includingpossible competitors, the MTS should have security protocols that keepdata, applications, and application use separate. Also, because manytenants may opt for access to an MTS rather than maintain their ownsystem, redundancy, up-time, and backup are additional functions thatmay be implemented in the MTS. In addition to user-specific data andtenant specific data, system 316 might also maintain system level datausable by multiple tenants or other data. Such system level data mightinclude industry reports, news, postings, and the like that are sharableamong tenants.

In certain embodiments, user systems 312 (which may be client systems)communicate with application servers 400 to request and updatesystem-level and tenant-level data from system 316 that may requiresending one or more queries to tenant data storage 322 and/or systemdata storage 324. System 316 (e.g., an application server 400 in system316) automatically generates one or more SQL statements (e.g., one ormore SQL queries) that are designed to access the desired information.System data storage 324 may generate query plans to access the requesteddata from the database.

Each database can generally be viewed as a collection of objects, suchas a set of logical tables, containing data fitted into predefinedcategories. A “table” is one representation of a data object, and may beused herein to simplify the conceptual description of objects and customobjects. It should be understood that “table” and “object” may be usedinterchangeably herein. Each table generally contains one or more datacategories logically arranged as columns or fields in a viewable schema.Each row or record of a table contains an instance of data for eachcategory defined by the fields. For example, a CRM database may includea table that describes a customer with fields for basic contactinformation such as name, address, phone number, fax number, etc.Another table might describe a purchase order, including fields forinformation such as customer, product, sale price, date, etc. In somemulti-tenant database systems, standard entity tables might be providedfor use by all tenants. For CRM database applications, such standardentities might include tables for Account, Contact, Lead, andOpportunity data, each containing pre-defined fields. It should beunderstood that the word “entity” may also be used interchangeablyherein with “object” and “table”.

In some multi-tenant database systems, tenants may be allowed to createand store custom objects, or they may be allowed to customize standardentities or objects, for example by creating custom fields for standardobjects, including custom index fields. U.S. patent application Ser. No.10/817,161, filed Apr. 2, 2004, entitled “Custom Entities and Fields ina Multi-Tenant Database System”, and which is hereby incorporated hereinby reference, teaches systems and methods for creating custom objects aswell as customizing standard objects in a multi-tenant database system.In certain embodiments, for example, all custom entity data rows arestored in a single multi-tenant physical table, which may containmultiple logical tables per organization. It is transparent to customersthat their multiple “tables” are in fact stored in one large table orthat their data may be stored in the same table as the data of othercustomers.

Reference in the specification to “one embodiment” or “an embodiment”means that a particular feature, structure, or characteristic describedin connection with the embodiment is included in at least one embodimentof the invention. The appearances of the phrase “in one embodiment” invarious places in the specification are not necessarily all referring tothe same embodiment.

While the invention has been described in terms of several embodiments,those skilled in the art will recognize that the invention is notlimited to the embodiments described, but can be practiced withmodification and alteration within the spirit and scope of the appendedclaims. The description is thus to be regarded as illustrative insteadof limiting.

What is claimed is:
 1. A system comprising: a plurality of hardwarecomputing systems each having one or more processors and at least onememory component coupled with the one or more processors, the pluralityof hardware computing systems to provide one or more instances of acomputing environment, wherein an instance is a self-containedarchitecture to provide at least one database with corresponding searchand file system and wherein the plurality of hardware computing systemshave associated categories comprising standard, standard data residency,public and public data residency; the plurality of hardware computingsystems to organize user information from the one or more instances ofthe computing environment as zones, wherein a zone is associated withone or more data residency requirements; and the plurality of hardwarecomputing systems to selectively obfuscate user information prior totransmitting blocks of data including the obfuscated user informationfrom a source zone to a destination zone, wherein the selectiveobfuscation is based on a corresponding category of the associatedcategories and on the data residency requirement.
 2. The system of claim1 wherein the computing environment comprises a multitenant environment,wherein a tenant comprises a group of users who share a common accesswith specific privileges to a specified instance.
 3. The system of claim2 wherein the multitenant environment provides each tenant with adedicated share of the specified instance including one or more oftenant specific data, user management, tenant-specific functionality,configuration, customizations, non-functional properties and associatedapplications.
 4. The system of claim 1 wherein a zone is associated withone or more characteristics of corresponding user information that aredifferent than the instance to which the user information belongs. 5.The system of claim 4 wherein the one or more characteristics compriseat least tenant information for the corresponding user information. 6.The system of claim 1 wherein data residency requirements comprise:personally identifiable information (PII) cannot leave standard dataresidency servers unobfuscated, PII cannot be sent to public or publicdata residency servers unobfuscated, and PII data in a public servercannot leave its geographic region.
 7. A method implemented within oneor more instances of a computing environment, wherein an instance is aself-contained architecture to provide at least one database withcorresponding search and file system, the method comprising: organizinguser information from the one or more instances of the computingenvironment as zones, wherein a zone is associated with one or more dataresidency requirements and the computing environment comprises multiplecomputing systems having associated categories comprising standard,standard data residency, public and public data residency; andselectively obfuscating user information prior to transmitting blocks ofdata including the obfuscated user information from a source zone to adestination zone, wherein the selective obfuscation is based on zoneinformation for the source zone and the destination zone, wherein theselective obfuscation is based on a corresponding category of theassociated categories and on the data residency requirement.
 8. Themethod of claim 7, wherein a zone is associated with one or morecharacteristics of corresponding user information that are differentthan the instance to which the user information belongs.
 9. The systemof claim 7 wherein the computing environment comprises a multitenantenvironment and the multitenant environment provides each tenant with adedicated share of a specified instance including one or more of tenantspecific data, user management, tenant-specific functionality,configuration, customizations, nonfunctional properties and associatedapplications.
 10. The system of claim 8 wherein the one or morecharacteristics comprise at least tenant information for thecorresponding user information.
 11. The system of claim 7 wherein dataresidency requirements comprise: personally identifiable information(PII) cannot leave standard data residency servers unobfuscated, PIIcannot be sent to public or public data residency servers unobfuscated,and PII data in a public server cannot leave its geographic region. 12.A non-transitory computer-readable medium having stored thereoninstructions that, when executed, are configurable to cause one or moreprocessors to provide one or more instances of a computing environment,wherein an instance is a self-contained architecture to provide at leastone database with corresponding search and file system, the instructionsfurther comprising instructions that, when executed by the one or moreprocessors, cause the one or more processors to: organize userinformation from the one or more instances of the computing environmentas zones, wherein a zone is associated with one or more data residencyrequirements and the computing environment comprises multiple computingsystems having associated categories comprising standard, standard dataresidency, public and public data residency; and selectively obfuscateuser information prior to transmitting blocks of data including theobfuscated user information from a source zone to a destination zone,wherein the selective obfuscation is based on zone information for thesource zone and the destination zone, wherein the selective obfuscationis based on a corresponding category of the associated categories and onthe data residency requirement.
 13. The method of claim 12, wherein azone is based on one or more characteristics of corresponding userinformation that are different than the instance to which the userinformation belongs.
 14. The system of claim 12 wherein the computingenvironment comprises a multitenant environment and the multitenantenvironment provides each tenant with a dedicated share of the specifiedinstance including one or more of tenant specific data, user management,tenant-specific functionality, configuration, customizations,nonfunctional properties and associated applications.
 15. The system ofclaim 13 wherein the one or more characteristics comprise at leasttenant information for the corresponding user information.
 16. Thesystem of claim 12 wherein data residency requirements comprise:personally identifiable information (PII) cannot leave standard dataresidency servers unobfuscated, PII cannot be sent to public or publicdata residency servers unobfuscated, and PII data in a public servercannot leave its geographic region.